Skip to content

feat(health): SDK health resource — record signals + read profile/cohort - #2

Merged
rrader26 merged 1 commit into
mainfrom
feat/health-resource
Jun 29, 2026
Merged

feat(health): SDK health resource — record signals + read profile/cohort#2
rrader26 merged 1 commit into
mainfrom
feat/health-resource

Conversation

@rrader26

Copy link
Copy Markdown
Contributor

What

Adds the tf.health resource to the SDK: record biomarker / demographic / condition signals for a subject and read back a wellness profile and cohort risk — decision-support framing, never a diagnosis.

Why

First domain resource on the SDK surface; pairs the engine's health estimators (e.g. PhenoAge bio-age) with a typed client.

Notes

  • This is the base of a stacked series. The SDK resource catch-up (typed-attributes, financial, and the v2 general-prediction surface) builds on top of this branch in a follow-up PR.

🤖 Generated with Claude Code

Adds tf.health for the memory engine's health vertical:

- Input (record* — health data IS memory data, stored as non-activity
  `fact` items so it feeds the health engine without polluting behavioral
  mining):
    recordBiomarker(subject, biomarker, value, { unit, observedAt })
    recordDemographics(subject, { ageYears, sex, weightKg, heightCm, activity })
    recordCondition(subject, { icd10, status, onsetAt })
- Read:
    getProfile(subject)        → biological age + condition predictions + biomarkers
    getCohortRisk(subject, {k}) → condition prevalence among similar patients

Callers decide where the data comes from (EHR, document extraction,
wearable, manual) — the SDK just gives the typed way in and out. Requires
the @thinkfleet/pack-healthcare pack on the project.

Wired into ThinkFleetMemory client + index exports + types/health.ts.
tsc --noEmit clean.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants